Configurable user interface systems for hospital bed

ABSTRACT

Configurable user interface systems for a patient support structure are disclosed. As described a control interface comprises the capability to allow limited impact on processes deemed important when other applications and programs are run. The configurable user interface systems described herein allow for customized display of information and display options available to a user in various environments.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This patent application claims the benefit of U.S. Provisional PatentApplication 61/653,726, filed on May 31, 2012, the entire disclosure ofwhich is hereby incorporated by reference.

BACKGROUND

The present disclosure relates to hospital beds and particularly theuser interface systems for hospital beds. More particularly, the presentdisclosure relates to configurable user systems for hospital beds. Whileseveral systems and methods exist for configuring user systems forhospital beds, a need exists for continued development in this area.

BRIEF SUMMARY

The present disclosure includes one or more of the features recited inthe appended claims and/or the following features which, alone or in anycombination, may comprise patentable subject matter.

One embodiment of a system for configuring a user interface of ahospital bed may comprise a graphical control interface which maycomprise a main processor and an auxiliary processor mounted on ahospital bed. The main processor and the auxiliary processor may beconfigured to selectively receive information from the software programresident on a computer based on location of said hospital bed. A displaydevice may be configured to be controlled by the graphical controlinterface based on information received from the software program.

Another embodiment of a system for configuring a user interface of ahospital bed may comprise a main processor and an auxiliary processor. Asoftware program resident on a computer may be configured to selectivelysend information to the main processor and the auxiliary processor. Adisplay device may be configured to selectively receive information fromsaid main processor and the auxiliary processor; display on said displaydevice may be configured to be controlled by information received fromsaid software program.

Another embodiment of a system for configuring a user interface of ahospital bed may comprise a graphical control interface comprising amain processor and an auxiliary processor. A network interface unit maybe configured to communicate with the graphical control interface. Ahospital communication network may be configured to communicate with thenetwork interface. The hospital communication network may comprise asoftware program resident on a computer configured to communicate withthe graphical control interface to selectively send information to themain processor and the auxiliary processor. A display device may beconfigured to selectively receive information from the main processorand the auxiliary processor, display on the display device may beconfigured to be controlled by information received from the softwareprogram.

One embodiment of a configurable user interface for a hospital bed maycomprise a main processor and an auxiliary processor which may beconfigured to communicate with the main processor. A network switch maybe configured to selectively transmit information to the main processorand the auxiliary processor based on a control signal received from asoftware program resident on a computer. A display device may beconfigured to be controlled by at least one of the main processor andthe auxiliary processor, the display on the display device may beconfigured to be modified based on information received from thesoftware program. A user input receiver may be configured to communicatewith at least one of the main processor and the auxiliary processor andmay be configured to receive user input.

One embodiment of a system for configuring a user interface of ahospital bed may comprise a graphical control interface which maycomprise a main processor and an auxiliary processor mounted on ahospital bed. The main processor and the auxiliary processor may beconfigured to selectively receive information from the software programresident on a computer based on identity of a patient occupying saidhospital bed. A display device may be configured to be controlled by thegraphical control interface based on information received from thesoftware program.

One embodiment of a hospital bed may comprise a patient supportstructure, a graphical interface and control circuitry coupled to thegraphical interface, the control circuitry may automatically signal thegraphical interface to alter at least one of available control functionsdisplayed on the graphical interface based upon at least one of alocation of the hospital bed within a healthcare facility and a type ofpatient supported on the patient support structure.

One embodiment of a hospital bed may comprise a patient supportstructure and a graphical interface comprising a main processor whichmay be configured to process core functions of said patient supportstructure and an auxiliary processor which may be configured to processadditional functions wherein said main processor and said auxiliaryprocessor may be in limited communication with each other, whereinfunctionality of said main processor may be configured to comply with aregulatory compliance standard.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings incorporated in and forming a part of thespecification illustrate several aspects of the claimed subject matterand, together with the description, serve to explain the principles ofthe claimed subject matter. In the drawings:

FIG. 1 is a block diagram of a system for configuring a user interfaceof a hospital bed, constructed according to one or more of theprinciples disclosed herein;

FIG. 2 is another block diagram of a system for configuring a userinterface of a hospital bed, constructed according to one or more of theprinciples disclosed herein;

FIG. 3 is a schematic of a hospital bed, the user interface of which isconfigured to be modified, constructed according to one or more of theprinciples disclosed herein;

FIG. 4 is another block diagram of some components of the system forconfiguring a user interface of a hospital bed, constructed according toone or more of the principles disclosed herein;

FIG. 5 is a block diagram of a system for configuring a user interfaceof a hospital bed, constructed according to one or more of theprinciples disclosed herein;

FIG. 6A and FIG. 6B are embodiments of a system for configuring a userinterface of a hospital bed wherein the user interface is configuredbased on patient identity, constructed according to one or more of theprinciples disclosed herein; and

FIG. 7A and FIG. 7B are embodiments of a graphical control interface foruse in a system for configuring a user interface of a hospital bed,constructed according to one or more of the principles disclosed herein.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The embodiments of the claimed subject matter and the various featuresand advantageous details thereof are explained more fully with referenceto the non-limiting embodiments and examples that are described and/orillustrated in the accompanying drawings and detailed in the followingdescription. It should be noted that the features illustrated in thedrawings are not necessarily drawn to scale, and features of oneembodiment may be employed with other embodiments as the skilled artisanwould recognize, even if not explicitly stated herein. Descriptions ofwell-known components and processing techniques may be briefly mentionedor omitted so as to not unnecessarily obscure the embodiments of theclaimed subject matter described. The examples used herein are intendedmerely to facilitate an understanding of ways in which the claimedsubject matter may be practiced and to further enable those of skill inthe art to practice the embodiments of the claimed subject matterdescribed herein. Accordingly, the examples and embodiments herein aremerely illustrative and should not be construed as limiting the scope ofthe claimed subject matter, which is defined solely by the appendedclaims and applicable law. Moreover, it is noted that like referencenumerals represent similar parts throughout the several views of thedrawings.

It is understood that the subject matter claimed is not limited to theparticular methodology, protocols, devices, apparatus, materials,applications, etc., described herein, as these may vary. It is also tobe understood that the terminology used herein is used for the purposeof describing particular embodiments only, and is not intended to limitthe scope of the claimed subject matter.

Unless defined otherwise, all technical and scientific terms used hereinhave the same meanings as commonly understood by one of ordinary skillin the art.

According to this disclosure, user interface screens of a hospital bed10 are configured differently depending on either the location of thehospital bed 10 within a healthcare facility of the type of patientsupported on the hospital bed or both. Thus depending upon patient typeor location, the user interface screens are altered so that differenttypes of functions are made available on the screen for use bycaregivers. Thus patients having different medical conditions orailments, for example will dictate the features of the hospital be 10that are made available for use and/or made unavailable via thegraphical user interface of the hospital bed 10.

One embodiment of a system for configuring a user interface for ahospital bed is shown in FIG. 1. As shown in FIG. 1 a graphical controlinterface (GCI) 12 is mounted on a patient support structure 10. Thepatient support structure 10 is a hospital bed in this embodiment butmay be a wheelchair or a stretcher in other embodiments. The GCI 12 is ascreen on which patient information is displayed as well as accepts userinputs such as controlling bed motors to raise and lower an upper framerelative to a base frame, moving mattress support deck sections,controlling mattress therapy functions such as rotation therapypercussion and vibration therapy and alternating pressure therapy. Inone embodiment, for patients in traction, some of the screens/functionsof the GCI 12 may be completely removed, for example the deckarticulation motors should not be moved and patient should not berotated. The GCI 12 is connected to a network interface unit (NIU) 16 bya wired connection in this embodiment. The GCI 12 is connected to theNIU 16 by an Ethernet cable, while in other embodiments the wiredconnection may be of any type including but not limited to optical fibercables. In this embodiment, the Ethernet cable connection between theGCI 12 and the NIU 16 comprises a quick disconnect coupling 14. Quickdisconnect coupling 14 is configured to allow the GCI 12 mounted on thebed to separate from the NIU 16 if the bed is wheeled away withoutdamage to the GCI 12, NIU 16 or the cables. Upon the connection betweenthe GCI 12 and the NIU 16 being disrupted, in one embodiment based ondecoupling at the quick disconnect coupling 14 the GCI 12 is configuredto alter the display into a transport mode. The NIU 16 comprises anEthernet port in this embodiment, while in another embodiment NIU 16comprises both the Ethernet port and an Ethernet switch. NIU 16 islocated behind the hospital room wall in this embodiment, in otherembodiments, NIU 16 may located anywhere including inside the hospitalroom and/or at a central hospital network station. NIU 16 is connectedto the hospital communication network 18 via an Ethernet connection inthis embodiment and configured to communicate with a software program 20resident on a computer. In other embodiments, the software program maybe resident on a server or a multitude of computers. The softwareprogram 20 is configured to communicate with an electronic medicalrecords (EMR) database 22 as shown in FIG. 1. NIU 16 is also configuredto communicate with a nurse call system 24. In this embodiment NIU 16communicates with the nurse call system 24 via a P379 type connectionwhile in other embodiments NIU 16 may communicate with the nurse callsystem 24 via any wired or wireless connection. As shown in FIG. 1, NIU16 is also configured to communicate with a low voltage controller 26which in this embodiment serves to control the room lighting. NIU 16 isconfigured to communicate with an audio-visual device 28 which in thisembodiment is a television. The GCI 12 allows for control inputs to besent to the television via the NIU 16 in this embodiment.

FIG. 2 shows another embodiment of a system for configuring a userinterface for a hospital bed. The GCI 12 is configured to communicatewith a wireless interface unit (WIU) 30 which it configured tocommunicate with a wireless access point 34 by means of antennas 32.Wireless access point 34 is also configured to communicate with asoftware program 20 resident on a computer which is part of a hospitalcommunication network 18. In this embodiment the wireless access point34 amplifies and/or filters the signal received from and/or sent to thewireless interface unit 32, in other embodiments the wireless accesspoint 34 serves as a router of the signal received. Software program 20resident on a computer is configured to communicate with an electronicmedical records database 22. In this embodiment the wireless accesspoint 34 is also configured to communicate with a nurse call system 24and/or a low voltage controller 26 and/or an audio-visual device 28wirelessly via antenna 32. In other embodiment any of theafore-mentioned connections to and from the wireless access point 34 maybe wired.

FIG. 3 shows a representational image of a bed with a GCI 12 which isconfigured to customize the display on a display device 56 based on bedlocation and/or patient identification and/or caregiver input as shownin FIG. 4 through FIG. 7B.

FIG. 4 is another block diagram of some components of the system forconfiguring a user interface of a hospital bed. As shown in FIG. 4, GCI12 comprises a main processor 36 with a main memory 38 and an auxiliaryprocessor 40 with auxiliary memory 42. Main memory 38 and auxiliarymemory 42 may be volatile and/or non-volatile type. The main processor36 and auxiliary microprocessor 40 are any programmable or preprogrammedtype devices capable of receiving a signal and processing it. In theembodiment shown in FIG. 4, the applications deemed as important to theoperation of the patient support structure 10 are processed by mainprocessor 36 and stored in the main memory 38. In this embodiment, theapplications include but are not limited to operation of the motors onthe patient support structure 10 and/or inflation of the mattress and/ordetermination of actual patient weight using weighing apparatusintegrated in the patient support structure 10. An operating systemand/or Controller Area Network (CAN) capabilities and/or TransmissionControl Protocol/Internet Protocol (TCP/IP) stack and/or other driversare also contemplated to be processed by the main processor 36. Severalsituations may arise wherein customized information or displays may bedesirable. In one prophetic example the ideal weight of a patient isdesirable since ideal weight correlates to the amount of bone marrow aperson has and therefore is useful for calculation of medication dosage.As shown in FIG. 5, FIG. 7A and FIG. 7B the display device 56 may eitherask the caregiver to input the ideal weight or the ideal weight is foundfrom the software 20 and/or the electronic medical records 22 anddisplayed on the display device 56. Auxiliary processor 40 is configuredto host applications for customized displays and interfaces such as thecase described in the aforementioned prophetic example. In thisembodiment the auxiliary processor 40 hosts applications for customizeddisplays as web applications, in other embodiments the applicationsand/or the web pages are stored in the auxiliary memory 42. Mainprocessor 36 is configured to communicate with the auxiliary processor40 and logical and/or hardware limitations 44 ensure that communicationwith auxiliary processor 40 does not overwhelm the main processor 36.Logical or software limits such as the percentage of processing capacityof the main processor 36 that may be occupied in communication with theauxiliary processor 40 ensure that the main processor 36 is notoverwhelmed by communication with the auxiliary processor 40. In otherembodiments, hardware limits such as physical limitations of the cableand/or other hardware components connecting the main processor 36 andthe auxiliary processor 40 ensure that the amount of processing capacityof the main processor 36 that can be used up by the auxiliary processor40 is limited. This strives to ensure that the main microprocessor 36has processing capacity accessible to applications deemed as important.

The GCI 12 is in communication with a software program 20 resident on acomputer. The software program 20 is configured to communicatealterations to pre-existing applications deemed as important and/oradd-on applications and/or third party web applications in variousembodiments. The software program 20 is configured to transmit theaforementioned information to the main processor 36 and/or auxiliaryprocessor 40. In this embodiment the software program 20 is configuredto communicate the aforementioned information selectively based onlocation of the patient support structure 10 and/or patientidentification and/or caregiver input. In other embodiments, any othercriteria may be used to transmit information from the software program20 and vice versa including but not limited to periodic software updatesand maintenance. In the embodiment in which location of the patientsupport structure 10 causes information to be selectively communicatedby the software program 20 to the main processor 36 and/or the auxiliaryprocessor 40, location information may be entered manually or beautomatically gathered based on any parameter including but not limitedto Media Access Control (MAC) address, IP address, wireless access pointinformation gained from communication between the GCI 12 and thehospital communication network 18. A few examples of tracking and/orlocation of equipment and personnel are found in U.S. Pat. Nos.7,450,024, 7,907,053, 7,734,476, and 7,248,933 all of which areincorporated by reference herein. In another embodiment, a dedicatedidentification device in the room may also be used to determine thelocation of a patient support structure 10 present in that room relativeto its location in the hospital. In one embodiment functionality of themain processor 36 is in compliance with at least one regulatory standard(one prophetic example being the Code of Federal Regulations) while theauxiliary processor 40 functionality does not impact the corefunctionality of the medical device and the auxiliary processor 40 hostsadd-on applications and/or third party web applications not subject toapproval and/or compliance requirements.

FIG. 5 shows another block diagram of some components of the system forconfiguring a user interface of a hospital bed. As shown in FIG. 5, asoftware program 20 resident on a computer is configured to communicatewith an electronic medical records database 22. The software program 20also communicates with the GCI 12 via an Ethernet and/or wirelessnetworking port. The GCI 12 comprises an Ethernet and/or wirelessnetworking switch 46 which is configured to communicate with theEthernet and/or wireless networking port, the main processor 36 and theauxiliary processor 40. The Ethernet and/or wireless networking port iselectrically isolated from the GCI in this embodiment to allow physicalisolation between the bed electronics and the Ethernet and/or wirelessnetworking port. In this embodiment an isolation transformer circuit isused while in other embodiments any other type of physical isolationmechanism may be used including but not limited to a fuse. Theaforementioned physical isolation ensures that a sudden spike in voltageand/or current experienced at the Ethernet and/or wireless networkingport is not transmitted to the GCI 12. The Ethernet and/or wirelessnetworking switch 46 is controlled by the software program 20 and isconfigured to selectively communicate information from the softwareprogram 20 to main processor 36 and the auxiliary processor 40. In thisembodiment the Ethernet and/or wireless networking switch 46 isconfigured to selectively communicate with the main processor 36 theauxiliary processor 40 by a TCP/IP type of communication protocol, whilein other embodiments, the Ethernet and/or wireless networking switch 46is configured to selectively communicate with the main processor 36 andthe auxiliary processor 40 using any type of protocol and/or hardwareincluding but not limited to fiber optical communication. The mainprocessor 36 and the auxiliary processor 40 are in communication via aCAN type connection in this embodiment, while in other embodiments themain processor 36 and the auxiliary processor 40 may be in communicationusing any other type of connection. Connection between the mainprocessor 36 and the auxiliary processor 40 is limited and is referredto as CAN 2 as opposed to the connections with other device moduleswhich are denoted as CAN1 in FIG. 5. The main processor 36 is alsoconfigured to communicate with the Ethernet and/or wireless networkingswitch 46 to setup communication information. Main processor 36 furthercomprises a main memory 36 which is configured to store at least one ofan operating system, Controller Area Network (CAN) capabilities,Transmission Control Protocol/Internet Protocol (TCP/IP) stack, otherdrivers, applications and web pages. The auxiliary processor 40comprises an auxiliary memory 42 which is configured to store webapplications, customized applications and web pages in this embodiment.In other embodiments, the main memory 38 and the auxiliary memory 42 areconfigured to store other information including but not limited toperformance data of various components of the patient support structure10, caregiver input to the GCI 12 and information for other devicemodules such as a patient identification system.

The main processor 36 and the auxiliary processor 40 are configured tocommunicate with a video multiplexer 52 via the main serializer 48 andthe auxiliary serializer 50 respectively. Main serializer 48 isconfigured to serialize the video and/or data from the main processor36. Main serializer 48 is configured to communicate with the videomultiplexer 52 to send and receive information. Auxiliary serializer 50is configured to serialize the video and/or data from the auxiliaryprocessor 40 and is configured to communicate with the video multiplexer52 to send and receive information. In this embodiment data between themain processor 36 and the main serializer 48 as is data between theauxiliary processor 40 and auxiliary serializer 50 is communicated usingSerial Data Protocol (SDP). In other embodiments, any other type of datacommunication protocol or means may be used. The video multiplexer 52 isin communication with a deserializer 54 which deserializes informationreceived from the multiplexer 52 and is configured to communicate theinformation to a display device 56. The deserializer 54 also receivesdata from a user input receiver 58 as shown in FIG. 5. Data received bythe desearializer 54 from the user input receiver 58 is transmitted tothe video multiplexer 52 and to the main processor 36 and/or auxiliaryprocessor 40 there from. Main processor 36 controls video multiplexer 52to selectively send information received from the main processor 36 andthe auxiliary processor 40 to the deserializer 54. Main processor 36also controls the flow of information from the video multiplexer 52 tothe main processor 36 and/or the auxiliary processor 40. A home button60 is configured to allow a user to reset the display on the displaydevice 56 to a predetermined state. Home button 60 is a physicalhardware component such as a switch, configured to communicate with themain processor 36 in this embodiment. In other embodiments the homebutton 60 may be an icon on a touch sensitive screen or any other typeof switch. The home button 60 allows a user to reset the display ondisplay device 56 and/or the system to a predetermined configuration incase the system ‘hangs’ or becomes otherwise inoperative.

FIG. 6A & FIG. 6B show embodiments of some components of systems forconfiguring a user interface of a hospital bed in which the identity ofthe patient alters the display and/or display options on a displaydevice 56. In another embodiment, identification of the patientsupported by the patient support apparatus 10 causes the softwareprogram 20 to transmit information to the GCI 12.

As shown in FIG. 6A, an identification tag 62 attached to a personsupported by the patient support apparatus 10 allows an identificationreader 64 to read the identification tag 62 in this embodiment. In theembodiment shown in FIG. 6A the identification tag 62 is associated witha Radio-frequency ID (RFID) which is recognized by the identificationreader 64. The patient is assigned a unique RFID stored in theidentification tag 62 upon admission into the hospital or anytimethereafter. In another embodiment the identification tag 62 isassociated with the patient support structure 10 and the identity of thepatient is determined by the software program 20 by accessing hospitalrecords to ascertain association of a particular patient with a patientsupport structure 10. In other embodiments, other types ofidentification tags 62 including but not limited to bar codes may beused along with the corresponding type of identification reader 64. Inthis embodiment, the identification reader 64 is in communication withthe GCI 12 and conveys the unique RFID to the GCI 12. GCI 12 transmitsthis information to the software program 20 which looks up the relationbetween the unique RFID and hospital records to establish associationbetween the unique RFID and patient identity. Upon identification of thepatient, the software program 20 is configured to transmit informationto the GCI 12 which would alter the display and/or display options on adisplay device 56. In one embodiment the correlation of the patient'sidentity to a condition and/or ailment results in the user interfacebeing altered.

In the embodiment shown in FIG. 6B, the identity of a patient supportedby the person support structure 10 is established by image recognition.An image capture device 66 is configured to capture the image of atleast a portion of the patient, in this embodiment the facial region. Inthis embodiment the image capture device 66 is configured to communicatewith a software program 20. The image captured by the image capturedevice 66 is transmitted to the software program 20 and is compared witha database of patient images. Software program 20 is thereby configuredto determine the identity of the patient upon which the software program20 is configured to transmit information to the GCI 12 which would alterthe display and/or display options on a display device 56. In thisembodiment the image capture device 66 is configured to transmitinformation directly to the software program 20, while in anotherembodiment information from the image capture device 66 is transmittedto the GCI 12 which in turn is communicated with the software program20. In FIG. 6A and FIG. 6B the communication between the GCI 12 and thesoftware program 20 is shown to be wireless, in another embodiment thiscommunication may be wired.

FIG. 7A and FIG. 7B show two embodiments of a graphical controlinterface 12. FIG. 7A shows a graphical control interface 12 with adisplay device 56 which is a touch sensitive screen. In anotherembodiment, the display device 56 may have the capability to onlydisplay images, but not accept user input. In this embodiment thedisplay device 56 comprises a portion of the display represented byselectable buttons which form the user interface receiver 58 portion ofthe touch sensitive display device 56. In this embodiment, selection ofthe button labeled Oncology by the user causes the display on thedisplay device to change to a display which has been pre-determined asbeing Oncology specific. Selection of the Oncology button in thisembodiment causes the main processor 36 to control the video multiplexerand allow the pre-determined Oncology specific application stored in theauxiliary memory 42 to be displayed. In another embodiment, selection ofthe Oncology button by the user is transmitted to the software program20 which in turn transmits the appropriate information to the mainprocessor 36 and/or the auxiliary processor 40. In the Oncology specificprophetic example of a display screen shown in FIG. 7A, ideal weight ofthe patient is displayed based on patient identification and byaccessing corresponding information from electronic medical records 22.In other embodiments, the ideal weight of the patient may be entered bythe caregiver and thereafter stored in the auxiliary memory 42 and/ormain memory 38 and/or the software program 20. The home button 60 asshown in FIG. 7A is a display on the user interface receiver portion 58which in this case is a touch sensitive screen.

In the embodiment of the GCI shown in FIG. 7B, the display device 56 isa liquid crystal display (LCD) screen. As contemplated in the embodimentof the GCI shown in FIG. 7B, location of the patient and/or identity ofthe patient is determined and in the prophetic example shown in FIG. 7B,an Oncology specific screen is displayed. In this embodiment thecaregiver enters the ideal patient weight using the user input receiver58 which in this case comprises physical buttons. A home button 60allows the main processor 36 to reset the display 56 to a predeterminedstate upon activation by the user.

The use of the terms “a” and “an” and “the” and similar referents in thecontext of describing the subject matter (particularly in the context ofthe following claims) are to be construed to cover both the singular andthe plural, unless otherwise indicated herein or clearly contradicted bycontext. Recitation of ranges of values herein are merely intended toserve as a shorthand method of referring individually to each separatevalue falling within the range, unless otherwise indicated herein, andeach separate value is incorporated into the specification as if it wereindividually recited herein. Furthermore, the foregoing description isfor the purpose of illustration only, and not for the purpose oflimitation, as the scope of protection sought is defined by the claimsas set forth hereinafter together with any equivalents thereof entitledto. The use of any and all examples, or exemplary language (e.g., “suchas”) provided herein, is intended merely to better illustrate thesubject matter and does not pose a limitation on the scope of thesubject matter unless otherwise claimed. The use of the term “based on”and other like phrases indicating a condition for bringing about aresult, both in the claims and in the written description, is notintended to foreclose any other conditions that bring about that result.No language in the specification should be construed as indicating anynon-claimed element as essential to the practice of the invention asclaimed.

Preferred embodiments are described herein, including the best modeknown to the inventor for carrying out the claimed subject matter. Ofcourse, variations of those preferred embodiments will become apparentto those of ordinary skill in the art upon reading the foregoingdescription. The inventor expects skilled artisans to employ suchvariations as appropriate, and the inventor intends for the claimedsubject matter to be practiced otherwise than as specifically describedherein. Accordingly, this claimed subject matter includes allmodifications and equivalents of the subject matter recited in theclaims appended hereto as permitted by applicable law. Moreover, anycombination of the above-described elements in all possible variationsthereof is encompassed unless otherwise indicated herein or otherwiseclearly contradicted by context.

The disclosures of any references and publications cited above areexpressly incorporated by reference in their entireties to the sameextent as if each were incorporated by reference individually.

We claim:
 1. A system for configuring a user interface of a hospitalbed, the system comprising: a graphical control interface mounted on ahospital bed, said graphical control interface comprising a mainprocessor and an auxiliary processor; a software program resident on acomputer, said main processor and said auxiliary processor configured toselectively receive information from said software program based onlocation of said hospital bed; a display device configured tocommunicate with said graphical control interface, said graphicalcontrol interface configured to control said display device based oninformation received from said software program.
 2. The system forconfiguring a user interface of a hospital bed of claim 1, wherein saidgraphical control interface is configured to communicate with saidsoftware program resident on a computer wirelessly.
 3. A system forconfiguring a user interface of a hospital bed, the system comprising: amain processor; an auxiliary processor; a software program resident on acomputer configured to selectively send information to said mainprocessor and said auxiliary processor; a display device configured toselectively receive information from said main processor and saidauxiliary processor, display on said display device configured to becontrolled by information received from said software program.
 4. Thesystem for configuring a user interface of a hospital bed of claim 5,further comprising a user input receiver to receive user input, saiduser input receiver configured to communicate with at least one of saidmain processor and said auxiliary processor.
 5. The system forconfiguring a user interface of a hospital bed of claim 4, wherein saidsoftware program selectively sends information to said main processorand said auxiliary processor based on user input.
 6. The system forconfiguring a user interface of a hospital bed of claim 3, wherein saidsoftware program is configured to selectively send information to saidmain processor and said auxiliary processor based on location of saidhospital bed.
 7. The system for configuring a user interface of ahospital bed of claim 3, wherein said software program is configured toselectively send information to said main processor and said auxiliaryprocessor based on the identity of a patient occupying said hospitalbed.
 8. A system for configuring a user interface of a hospital bed, thesystem comprising: a graphical control interface, said graphical controlinterface comprising a main processor and an auxiliary processor; anetwork interface unit, configured to communicate with said graphicalcontrol interface; a hospital communication network configured tocommunicate with said network interface, said hospital communicationnetwork comprising a software program resident on a computer configuredto communicate with said graphical control interface to selectively sendinformation to said main processor and said auxiliary processor; adisplay device configured to selectively receive information from saidmain processor and said auxiliary processor, display on said displaydevice configured to be controlled by information received from saidsoftware program.
 9. The system for configuring a user interface of ahospital bed of claim 8 further comprising an electronic medical recorddatabase, said software program configured to access said electronicmedical record database.
 10. The system for configuring a user interfaceof a hospital bed of claim 8 further comprising a nurse call system,said network interface unit configured to communicate with said nursecall system.
 11. The system for configuring a user interface of ahospital bed of claim 8, said network interface unit configured tocommunicate with an audio-visual device.
 12. The system of configuring auser interface of a hospital bed of claim 8, said network interface unitconfigured to communicate with lighting controls of a hospital room. 13.The system of configuring a user interface of a hospital bed of claim 8further comprising a quick disconnect coupling between said graphicalcontrol interface and said network interface unit.
 14. The system ofconfiguring a user interface of a hospital bed of claim 8 wherein saidnetwork interface communicates with at least one of said graphicalinterface unit and said hospital communication network wirelessly.
 15. Aconfigurable user interface for a hospital bed comprising: a mainprocessor; an auxiliary processor configured to communicate with saidmain processor; a network switch configured to selectively transmitinformation to said main processor and said auxiliary processor based ona control signal received from a software program resident on acomputer; a display device configured to be controlled by at least oneof said main processor and said auxiliary processor, display on saiddisplay device configured to be modified based on information receivedfrom said software program; a user input receiver configured tocommunicate with at least one of said main processor and said auxiliaryprocessor, said user input receiver is configured to receive user input.16. The configurable user interface for a hospital bed of claim 15further comprising a serializer configured to communicate with at leastone of said main processor and said auxiliary processor.
 17. Theconfigurable user interface for a hospital bed of claim 16 furthercomprising a video multiplexer configured to multiplex signals at leastone of received from and sent to said serializer.
 18. The configurableuser interface for a hospital bed of claim 17 further comprising adeserializer configured to communicate with said multiplexer and saiddisplay device.
 19. The configurable user interface for a hospital bedof claim 15, wherein at least a portion of said display device is atouch sensitive screen and serves as a user input receiver.
 20. Theconfigurable user interface for a hospital bed of claim 15, wherein userinput via said user input receiver modifies display on said displaydevice.
 21. The configurable user interface for a hospital bed of claim15, wherein said software program is configured to selectively sendinformation to said main processor and said auxiliary processor based onlocation of said hospital bed.
 22. The configurable user interface for ahospital bed of claim 15, wherein said software program is configured toselectively send information to said main processor and said auxiliaryprocessor based on the identity of a patient occupying said hospitalbed.
 23. The configurable user interface for a hospital bed of claim 15,further comprising a switch, said switch configured to modify display onsaid display device to a predetermined configuration when activated by auser.
 24. A system for configuring a user interface of a hospital bed,the system comprising: a graphical control interface mounted on ahospital bed, said graphical control interface comprising a mainprocessor and an auxiliary processor; a software program resident on acomputer, said main processor and said auxiliary processor configured toselectively receive information from said software program based onidentity of a patient occupying said hospital bed; a display deviceconfigured to communicate with said graphical control interface, saidgraphical control interface configured to control said display devicebased on information received from said software program.
 25. A hospitalbed comprising: a patient support structure; a graphical interface; andcontrol circuitry coupled to said graphical interface, the controlcircuitry automatically signaling the graphical interface to alter atleast one of available control functions displayed on said graphicalinterface and information that is displayed on the graphical interfacebased upon at least one of a location of said hospital bed within ahealthcare facility and a type of patient supported on said patientsupport structure.
 26. The hospital bed of claim 25 wherein saidgraphical interface is configured to communicate with an electronicmedical records database.
 27. The hospital bed of claim 25 furthercomprising an alarm configured to be activated by said graphicalinterface.
 28. A hospital bed comprising: a patient support structure; agraphical interface comprising a main processor configured to processcore functions of said patient support structure and an auxiliaryprocessor configured to process additional functions wherein said mainprocessor and said auxiliary processor are in limited communication witheach other, wherein functionality of said main processor is configuredto comply with a regulatory compliance standard.